Skip to content

ci: fix Release Please and automate standalone release assets - #23

Merged
m4sh-wacker merged 1 commit into
mainfrom
fix/release-please-and-standalone-asset
Nov 21, 2026
Merged

m4sh-wacker merged 1 commit into
mainfrom
fix/release-please-and-standalone-asset

Conversation

@m4sh-wacker

Copy link
Copy Markdown
Collaborator

Release management

Release Please now uses the root package’s existing v0.1.0 tag as its baseline. The Node strategy keeps the package, lockfile, manifest, and changelog in sync. Conventional Commits populate the existing Added, Changed, Fixed, Security, and Maintenance headings. Ordinary documentation, chore, CI, build, test, and style commits do not trigger a release.

The workflow retains skip-labeling and restores the pending marker that the pinned action uses to recognize its own release PR after merge. The pinned changelog generator has no option to include commit authors in individual entries.

Standalone HTML

When Release Please creates a release, the same workflow checks out its exact tag, builds on Node.js 22.23.5, and uses the tagged commit time for the embedded build timestamp. It checks the package version and nonempty HTML, uploads only OWASP-DecodeBox-Standalone-vX.Y.Z.html, sets the release title, and verifies the uploaded filename and SHA-256 digest. Release Please retains ownership of the release notes.

For recovery, run Release Please from main with an existing stable tag in release_tag. This bypasses release creation and rebuilds the matching asset. The original v0.1.0 release is protected.

Verification

  • Ran the pinned Release Please engine against the actual history and release metadata. Current main produced no release candidate. A simulated future fix compared v0.1.0...v0.1.1 and excluded all ten historical fixes listed in chore(release): OWASP DecodeBox v0.1.1 #19.
  • Exercised every configured commit type, the pre-1.0 breaking-change bump, and the four version/changelog file updates. Validated the official JSON schema, workflow syntax, and action pins.
  • Ran a clean install, lint, typecheck, all 1,205 tests, and the production build. Two clean builds of the same tag produced identical HTML hashes. Opened the standalone file offline and checked its displayed version.
  • Exercised upload and recovery success and failure paths with simulated GitHub responses. No release was published during verification.

PR #19 still proposes the obsolete bump under the configuration on main. The first run after this change lands can reevaluate it.

@m4sh-wacker
m4sh-wacker merged commit 3a38673 into main Nov 21, 2026
6 checks passed
@m4sh-wacker
m4sh-wacker deleted the fix/release-please-and-standalone-asset branch November 21, 2026 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant